data(sdks): SDK primary-purpose boundary + remove Filecoin protocol/proving infrastructure libraries (DBIP #3703) - #3744

### Category boundary (SDK eligibility)

An offer qualifies for the SDK category when its **primary documented purpose** is giving
application developers a reusable library, SDK or framework for:

* building applications on the chain;
* building smart contracts or chain integrations;
* interacting with the chain from applications;
* deploying or testing blockchain applications;
* integrating application-level functionality with the chain.

Being technically useful inside the ecosystem is not sufficient by itself.

**Protocol-infrastructure exclusion.** An offer is *not* an SDK merely because it is
chain-specific or importable by developers. When the primary product job is implementing the
protocol, a node/client, consensus or consensus-adjacent infrastructure, storage/proving
infrastructure, protocol cryptography, chain-runtime internals, validator/miner/operator
infrastructure, or an internal component primarily consumed by the chain's own implementation,
do not classify it as an SDK unless its official documentation establishes a separate, supported
application-development use case (application-facing exception).

**Primary-consumer test:**

| Primary documented consumer | SDK? |
| --- | --- |
| dApp / application developers | Yes |
| Smart-contract developers | Yes |
| Developers integrating chain functionality into applications | Yes |
| Developers building/testing/deploying chain applications | Yes |
| Node/client implementers | No, unless an explicit application-facing interface is established |
| Protocol implementers | No |
| Consensus/proving/storage-infrastructure operators | No |
| Internal chain-implementation components | No |

**Product identity takes precedence over repository labels.** Classification follows the actual
product purpose per official documentation; labels such as "SDK", "library", "API", "framework",
"toolkit" or "infrastructure" never determine the category on their own.

Where an existing category already fits, use it. Where none fits, do not force the offer into
SDK; propose a category decision through the normal DBIP process.

- Protocol/chain-infrastructure libraries (node/client, consensus, proving, storage-proof, protocol-cryptography, chain-runtime internals) whose primary consumers are chain clients or protocol implementers, unless an application-facing interface is documented

- [ ] Its primary documented consumers are application/dApp/contract developers, not node or protocol implementers